Release 10.1A: OpenEdge Development:
Java Open Clients

Selecting an Open Client Runtime package

Based on the run-time configuration you want to support, you have the option of selecting any of the following Open Client Runtime distribution packages:

Basic Open Client Runtime packages — Supports the AppServer and AppServerDC URL connection protocols on an intranet.
SSL Open Client Runtime packages — Supports the AppServer, AppServerS, AppServerDC, and AppServerDCS URL connection protocols on an intranet.
HTTP Open Client Runtime packages — Supports the AppServer, AppServerDC, and HTTP URL connection protocols for both the Internet or an intranet. These packages support user-implemented authentication to a Web server and Proxy servers.
HTTPS Lite Open Client Runtime packages — Supports the AppServer, AppServerDC, HTTP, and HTTPS URL connection protocols for both the Internet or an intranet. These packages support a minimal set of HTTPS (SSL) functionality, for faster downloading. Progress Software Corporation recommends you use these packages for applets when minimizing download time is critical.

The packages above support many, but not all, SSL-enabled Web servers. The SSL configuration for the individual Web server and the digital certificate used to authenticate the Web server identity determines whether you can use these packages.

The packages above support user-implemented authentication to a Web server, data encryption, and Proxy servers.

HTTPS Standard Open Client Runtime packages — Supports the AppServer, AppServerDC, HTTP, and HTTPS URL connection protocols for both the Internet or an intranet. These packages provide a full set of HTTPS (SSL) functionality. Use them when download time is not critical.

These packages support most SSL-enabled Web servers. The individual Web server's SSL configuration and the digital certificate used to authenticate the identity of the Web server determines whether you can use these packages.

These packages support user-implemented authentication to a Web server, data encryption, and Proxy servers.

Note: If you use the HTTP, HTTPS Lite, or HTTPS Standard Packages, you must have a Web server hosting the AppServer Internet Adapter (AIA) Java servlet to support the HTTP/S protocol. Also, for every Web server that hosts an AIA servlet and supports the HTTPS protocol, the client machine must have the root digital certificate of the Certificate Authority that issued the digital certificate for the Web server.

As you develop your HTTPS, AppServerS, and AppServerDCS applications, you should consider that the application deployer might require certain data encryption and digital signature algorithms when they configure their Web server’s.

Your HTTPS requirements might exceed the capabilities of the HTTPS Lite package you select. Deployers also might require the use of SSL version 2 or TLS protocols instead of the standard SSL version 3. If any of these requirements exists, you must use the HTTPS Standard packages.

For more information about selecting a package, see Table 1–1. It lists types of supported applications, supported protocols, and Open Client Runtime packages you would use depending on the run-time configuration of your application and the protocols you want to support.

Table 1–1: Open Client package options

If your application run-time configuration is...	And the supported protocol is...	The Open Client Runtime package you use is...
A Java application, Java servlet, or Java applet running in the Netscape browser.	AppServer or AppServerDC	Basic (java/o4glrt.jar) (Recommended for intranet network configurations.)
	AppServerS or AppServerDCS	SSL (java/o4glrts.jar) (Recommended for intranet network configurations.)
	HTTP	HTTP (java/o4glrth.jar)
	HTTPS	HTTPS Lite (java/o4glrthsl.jar)      — OR — HTTPS Standard (java/o4glrths.jar)
A Java applet running in the Internet Explorer browser.	AppServer or AppServerDC	Basic (java/o4glrt.cab) (Recommended for Intranet network configurations.)
	AppServerS or AppServerDCS	SSL (java/o4glrts.cab) (Recommended for Intranet network configurations.)
	HTTP	HTTP (java/o4glrth.cab)
	HTTPS	HTTPS Lite (java/o4glrthsl.cab)      — OR — HTTPS Standard (java/o4glrths.cab)

All packages support the AppServer protocol, and the HTTPS packages support HTTP.

For example, based on the options described in Table 1–1, if you have:

An Intranet UNIX Java application that requires only AppServer support, you would use o4glrt.jar.
An Internet Explorer Java Applet that requires HTTP and limited HTTPS support, you would use o4glrthsl.cab.
A Java application that uses AppServer, AppServerDC, or HTTP, you would use o4glrth.jar.
A Java application that uses SSL-based AppServer connections (AppServerS or AppServerDCS), you would use o4glrts.jar.

Table 1–2 lists the security supported by each Open Client Runtime package.

Table 1–2: Security supported by package

For this package ...	This security is supported ...
Basic	User-implemented authentication using a userid and password.
SSL	Authentication that includes: User-implemented authentication using a userid and password. SSL V2, SSL V3, and TLS V1, Digital Signatures: RSA w. MD5, RSA w. SHA1, DSA 2. SHA1, and Key Exchange: RSA, Diffie-Hellman. Data encryption using RC4-128 bit key, RC4-40 bit key, DES-56 bit key, DES-40 bit key, Triple-DES-168 bit key, RC2-40 bit key.
HTTP	Authentication that includes: User-implemented authentication using a userid and password. Basic authentication to the AIA's Web server. Basic Proxy server authentication. Proxy servers.
HTTPS Lite (limited security)	Authentication that includes: User-implemented authentication using a userid and password. Basic Proxy server authentication. HTTP Basic authentication to the AIA's Web server. HTTPS using SSL V3, RSA with MD5 digital signatures, and RSA Key Exchange. Data encryption using RC4-128 bit key and RC4-40 bit key. Proxy servers.
HTTPS Standard (full security)	Authentication that includes: User-implemented authentication using a userid and password. Basic Proxy server authentication. HTTP basic authentication to the AIA's Web server. HTTPS using SSL V2, SSL V3, and TLS V1, Digital Signatures: RSA w. MD5, RSA w. SHA1, DSA 2. SHA1, and Key Exchange: RSA, Diffie-Hellman. Data encryption using RC4-128 bit key, RC4-40 bit key, DES-56 bit key, DES-40 bit key, Triple-DES-168 bit key, RC2-40 bit key. Proxy servers.